Use this window to confirm or cancel your request to remove the installed internal code changes and to activate their previous change levels for the selected Central Processor Complexes (CPCs).
Removing the installed changes and activating their previous change levels makes the previous levels operational.
At this point in the task, installed internal code changes are:
Task
Use this window to complete the following task. Select the task for examples with step-by-step instructions.
Internal code change process
The window displays a summary of the internal code change process recommended by IBM. Removing and activating internal code changes is not part of the process. But review the process before continuing.
Removing and activating internal code changes will undo the fourth step (step D) of the process for the current, installed changes. You should eventually install and activate the current changes again, to complete the process for those changes.
You should confirm your request to remove and activate internal code changes only if it is necessary to resolve a problem that occurred after installing and activating the current changes.
Mirroring support element data
Mirroring support element data copies it from a CPC's primary support element to its alternate support element. By regularly mirroring support element data, you help ensure the alternate support element will look and work the same as the primary support element, should you ever need to switch to using the alternate support element (due to a primary support element hardware failure, for example).
Ordinarily, support element data is mirrored automatically each day. But you can use the Alternate Support Element task to mirror support element data immediately, at any time and for any reason. For example, you may want to mirror support element data immediately after removing internal code changes on the primary support element, to ensure the alternate support element is at the same internal code level right away (otherwise, the alternate support element would remain at the previous internal code level until its daily, automatic mirroring occurred).
Concurrent internal code changes
Activating concurrent internal code changes does not require activating the CPCs on which the changes are installed. For this reason, activating the internal code changes is considered a concurrent operation. That is, it occurs while the CPCs and their operating systems continue to operate.
You can confirm your request to remove and activate concurrent internal code changes without affecting the operating system activity of the selected CPCs.